-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
front: fix results display when entering a scenario #10963
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## dev #10963 +/- ##
==========================================
- Coverage 81.60% 81.60% -0.01%
==========================================
Files 1095 1095
Lines 110431 110438 +7
Branches 742 742
==========================================
+ Hits 90121 90125 +4
- Misses 20268 20271 +3
Partials 42 42
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested, LGTM but left a comment
front/src/modules/simulationResult/components/SpeedSpaceChart/useSpeedSpaceChart.ts
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lgtm and tested, good job ! Could you put a description in the commit to explain the bug ?
Some getPathProperties conditions were not in the useEffect depths, so changing these values did not update trainSimulation (which is undefined by default when entering a scenario), preventing the simulation results to be displayed Signed-off-by: theocrsb <[email protected]>
f5db792
to
25e5ac5
Compare
I just added the description to the commit :) |
closes #10946
Some
getPathProperties
conditions were not in the useEffect depths, so changing these values did not updatetrainSimulation
(which is undefined by default when entering a scenario), preventing the simulation results to be displayed